Processed document archiving

Processed documents for both connections and trading partners can be archived on a local basic runtime or runtime cluster or a private runtime cloud. Processed document archiving is useful for auditing transactions or for viewing series of documents end-to-end, such as purchase order flows, that extend over multiple months.

On a runtime for which processed document archiving is enabled, archiving occurs according to the runtime’s purge schedule. When the scheduled purging of processed documents, execution logs, and temporary data occurs, processed documents are archived in a designated archive directory.

The archive directory is designated by the runtime cloud owner or local runtime owner. The destination directory for archiving for cloud attachment is actually a sub-directory of the runtime cloud’s archive directory. For example, if runtime cloud C’s archive directory is /C and runtime A is attached to runtime cloud C, runtime A’s archives are written to /C/A.

The archive directory is managed by the runtime owner. The data in the archive directory is not purged. If the archive directory is changed, it is the responsibility of the runtime owner to manually copy previously archived documents from the old archive directory to the new one.

note

An extra-cost, companion option called Extended Process Reporting Archive is available for local basic runtimes and runtime clusters and private runtime clouds whereby document metadata is stored for an additional 18 months. **This option is not available for the public Boomi runtime cloud.**If this option is enabled, document metadata continues to be accessible during the extended storage period in Executions, Documents, and Trading Partner lists in the Process Reporting page (Manage > Process Reporting). Archived documents are linked from those lists to enable easy retrieval. To have this option enabled for your account, contact your representative. For more information, see the Boomiverse article Document Archiving Options.

Configuring archiving for a basic runtime attached to a private runtime cloud

Assuming the archiving feature is enabled for both a runtime cloud owner’s account and the account of the owner of a cloud attachment, in order for archiving to occur on that runtime, the following configuration tasks must be performed:

1. The runtime cloud owner must designate the runtime cloud’s archive directory by setting the property Processed Document Archive Directory on the Advanced tab of the Cloud Properties panel in Manage > Runtime Management.

2. The runtime cloud owner must enable archiving for the runtime cloud by turning on the property Archive Processed Documents on the Advanced tab in the Cloud Properties panel in Manage > Runtime Management.

3. The runtime cloud owner must allow archiving to be enabled on the runtime by setting the property Enable Processed Document Archiving for the runtime on the Attachment Quotas tab in Manage > Cloud Management.

4. The runtime owner must enable archiving by turning on the property Archive Processed Documents on the Advanced tab of the Account Properties panel in Manage > Runtime Management.

When the runtime cloud is restarted, if the designated archive directory does not already exist, it is automatically created.

Configuring archiving for a local basic runtime or runtime cluster

If the archiving feature is enabled for the account of the owner of a local basic runtime or runtime cluster, the owner must set two properties on the Advanced tab of the Runtime Properties panel or cluster Properties panel in Manage > Runtime Management for achiving to occur:

1. Designate the archive directory by setting Processed Document Archive Directory.

2. Enable archiving by turning on Archive Processed Documents.

When the basic runtime or runtime cluster is restarted, if the designated archive directory does not already exist, it is automatically created.